Closes: #9838

Description

This PR increases the app's resilience when ProductVariation fields have unexpected types:

• When a variation's SKU is a number instead of a String.
• When a variation's weight is a number instead of a String.

It uses failsafe decoding to handle those alternative types, and adds to the unit test for parsing alternative types in a ProductVariation. (These are known decoding errors that users have experienced.)

Testing instructions

1. Set a breakpoint in your tool of choice for requests to the /wc/v3/products endpoint.
2. Build and run the app.
3. Open the Products tab.
4. Select a variable product.
5. Select the Variations section in product details.
6. Modify the response in one or both of the following ways:
   • A variation's SKU is a number (e.g. "sku": 123 or see the product-variation-alternative-types.json mock for an example).
   • A variation's weight is a number (e.g. "weight": 213).
7. Execute the response and confirm the app loads the variation list.

Screenshots

Before	After

• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.